Summary

This PR adds support for using an async context (specifically from the InvokeStore package) in the Logger utility. This allows users to emit log statements that are isolated specifically to the current lambda invocation, isolated from any other executions.

Changes

• Added a specific storage class for log attributes: LogAttributesStore
• The Logger class only accesses the data in this store through this interface and never touches the stored objects directly.
• Updated all methods that stored log attributes and log keys to use the new storage class.
• The storage class checks whether it is running in the InvokeStore context: if they are then the log keys are stored in the current async context, otherwise we fallback to a plain instance wide object as per the current implementation.
• Moved the sequence testing function to the common testing package.
• Added specific concurrency tests to ensure isolation is working as intended for the LogAttributesStore and theLogger class as a whole.

Issue number: closes #4667

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.